Gateway management using virtual gateways and wildcards

ABSTRACT

Systems, methods, and media for managing gateways. In an embodiment, a virtual gateway is generated which comprises a representation of each of one or more active scripts and/or device information (e.g., device drivers, and/or definitions and/or configurations for devices, device types, and/or device groups) stored on at least one remote physical gateway. At least one user interface is provided for editing each of the one or more active scripts and/or device information represented in the virtual gateway. Synchronization is automatically maintained, across at least one network, between the one or more active scripts and/or device information represented in the virtual gateway and the one or more active scripts and/or device information stored on the at least one remote physical gateway.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application claims priority to U.S. Provisional Patent App. No.61/952,655, filed on Mar. 13, 2014 and entitled “Systems and Methods forNetwork-Based Control of Physical Features of a Facility,” the entiretyof which is hereby incorporated herein by reference.

BACKGROUND

Field of the Invention

The embodiments described herein are generally directed to themanagement of gateways, and, more particularly, to the management ofcontrol scripts and/or drivers on physical gateways via virtualgateways.

Description of the Related Art

The use of machine-to-machine (M2M) systems is and will continue to be aprevalent aspect of commerce and society. M2M systems are an integralpart of the Internet of Things (IoT), and have a wide range ofapplications, including monitoring and control for industrial andbuilding automation, smart facilities, smart grids, smart cities,healthcare, hospitality, food services, and the like.

In M2M and IoT ecosystems, communications between devices in amachine-to-machine system may be performed using a gateway devicepositioned between the devices. The gateway device may also provideadditional services, such as the secure execution of applications,including control, monitoring, reporting, and alerting scripts, theconfiguration and activation/deactivation of one or more devices, devicetypes, and/or device groups, and data capture and reporting for devices,device types, and/or device groups communicatively connected to thegateway device.

As a simple example, in the context of industrial automation, variousdevices within a physical facility may be communicatively connected to agateway device for the facility. These devices may comprise sensors(e.g., temperature sensors, open/closed sensors, locked/unlockedsensors) and operable devices, such as doors, windows, locks, lights,gates, valves, etc. The gateway device may execute one or more controlscripts which monitor one or more of the devices (e.g., by receivingtemperature measurements from a temperature sensor, receiving the statusof a door lock, etc.) and control one or more of the devices based onthe monitoring of other devices and/or conditions (e.g., turning on alight if a gate is opened, unlocking or locking a door at a certaintime, sounding an alarm if a temperature exceeds a certain threshold,etc.).

In distributed monitoring and control systems (e.g., over a largefacility or over multiple geographically-dispersed facilities), multiplegateways may communicate with each other and/or a central platform overone or more networks (e.g., the Internet). In such situations, there maybe numerous gateways (e.g., hundreds) that must be configured,installed, operated, and managed. This can make it difficult to ensurethat each gateway and any associated scripts and devices, device types,and/or device groups have been properly configured, tested, implemented,updated, or backed up to ensure expected operation.

Thus, what are needed are technologies that enable more efficientmanagement of gateways, including the definition of gateways, scripts,and devices, device types, and/or device groups, configuration, testing,implementation, update, and recovery within M2M, IoT, cloud-based,and/or distributed-server-based systems.

SUMMARY

Accordingly, systems, methods, and media are disclosed for managinggateways.

In an embodiment, a system is disclosed. The system comprises: at leastone hardware processor; and one or more modules that, when executed bythe at least one hardware processor, generate a virtual gateway whichcomprises a representation of each of one or more active scripts andactive devices information (e.g., device drivers, and/or definitionsand/or configurations for devices, device types, and/or device groups)stored on at least one remote physical gateway; provide at least oneuser interface for editing each of the one or more active scripts andactive information represented in the virtual gateway; and automaticallymaintain synchronization, across at least one network, between the oneor more active scripts and active device information represented in thevirtual gateway and the one or more active scripts and active deviceinformation stored on the at least one remote physical gateway.

In another embodiment, a method is disclosed. The method comprises usingat least one hardware processor to: generate a virtual gateway whichcomprises a representation of each of one or more active scripts andactive information stored on at least one remote physical gateway;provide at least one user interface for editing each of the one or moreactive scripts and active device information represented in the virtualgateway; and automatically maintain synchronization, across at least onenetwork, between the one or more active scripts and active informationrepresented in the virtual gateway and the one or more active scriptsand active device information stored on the at least one remote physicalgateway.

In another embodiment, a non-transitory computer-readable medium havinginstructions stored thereon is disclosed. The instructions, whenexecuted by a processor, cause the processor to: generate a virtualgateway which comprises a representation of each of one or more activescripts and active device information stored on at least one remotephysical gateway; provide at least one user interface for editing eachof the one or more active scripts and active device informationrepresented in the virtual gateway; and automatically maintainsynchronization, across at least one network, between the one or moreactive scripts and active device information represented in the virtualgateway and the one or more active scripts and active device informationstored on the at least one remote physical gateway.

BRIEF DESCRIPTION OF THE DRAWINGS

The details of the present invention, both as to its structure andoperation, may be gleaned in part by study of the accompanying drawings,in which like reference numerals refer to like parts, and in which:

FIG. 1 illustrates an infrastructure in which embodiments of disclosedsystems, methods, and media may operate, according to an embodiment;

FIG. 2 illustrates systems for synchronizing gateways, according to anembodiment;

FIG. 3 illustrates systems for mirroring and synchronizing a script to aplurality of gateways, according to an embodiment;

FIG. 4 illustrates a process for editing an editable component of agateway, according to an embodiment;

FIG. 5 illustrates a process for synchronizing a gateway, according toan embodiment;

FIG. 6 illustrates a process for dereferencing wildcards in a script,according to an embodiment; and

FIG. 7 illustrates a processing system on which one or more of theprocesses described herein may be executed, according to an embodiment.

DETAILED DESCRIPTION

In an embodiment, systems, methods, and media are disclosed for themanagement of gateways, including the execution, creation,configuration, testing, implementation, operation, updating, backing-up,and recovery of virtual gateways, physical gateways, control scripts,and/or device information (e.g., device drivers, and/or definitionsand/or configurations for devices, device types, and/or device groups).After reading this description, it will become apparent to one skilledin the art how to implement the invention in various alternativeembodiments and alternative applications. However, although variousembodiments of the present invention will be described herein, it isunderstood that these embodiments are presented by way of example andillustration only, and not limitation. As such, this detaileddescription of various embodiments should not be construed to limit thescope or breadth of the present invention as set forth in the appendedclaims.

There are at least five major challenges in the design, testing,implementation, operation, and recovery of distributed M2M and IoTecosystems:

(1) Device, device type, and device group identification, definition,configuration, curation, operation, updating, performance analysis,recovery, and communications;

(2) Script creation, operational/performance testing, curation,implementation, and updating for device and gateway operation,monitoring, control, performance analysis, recovery, and management;

(3) Gateway configuration, creation, operational/performance testing,curation, implementation, updating, recovery, performance analysis, andmanagement;

(4) Efficient M2M and IoT ecosystem design, testing, implementation,operation, recovery, and management; and

(5) Efficient integration and implementation of new devices, devicetypes, device groups, scripts, communications, control protocols, andindustry standards into M2M and IoT ecosystems.

Certain embodiments disclosed herein address these challenges, forexample, through one or more of the following:

(1) Providing the capability for entitled users (e.g., granted specificaccess, authority, and permission to access selected defined physicaland/or logical components in an ecosystem and/or execute selecteddefined physical and/or logical functions in the ecosystem) to create,define, and test virtual representations of particular devices, devicetypes, and/or device groups, thereby enabling these entitled users to:

-   -   (a) Define the properties, associated values, and        communications/control protocols (e.g., BACnet, EnOcean,        Bluetooth Low Energy, etc.) for a particular virtual device        (e.g., a specific model of thermostat);    -   (b) Define the properties, associated values, and        communications/control protocols for a particular type of        virtual device (e.g., any model of thermostat);    -   (c) Define the properties, associated values, and        communications/control protocols for a group of virtual devices        (e.g., a building HVAC system, which could include, without        limitation, one or more thermostats, boiler controllers, CO2 gas        detectors, gas shut-off valves, chiller controllers, water        detectors, water shut-off valves, damper controllers, occupancy        detectors, sunlight sensors, etc.);    -   (d) Define virtual gateway loads for communications/control        protocols, processing, memory, and data storage for virtual        devices, virtual device types, and/or virtual device groups;        and/or    -   (e) Utilize wildcard(s) for virtual devices, virtual device        types, and/or virtual device groups that, when scripts        containing such wildcard(s) are activated and implemented on one        or more physical gateways, are automatically replaced        (“dereferenced”) by an identifier or other representation of a        particular physical device, particular type of device, and/or        particular group of devices that are communicatively connected        to those physical gateways, such that all applicable associate        property values assigned for the physical device, type of        device, and/or group of devices are automatically updated to        those defined in their corresponding virtual representations;

(2) Providing the capability for entitled users to create, define, andtest scripts in the virtual environment, including:

-   -   (a) Creating scripts and assigning virtual devices, device        types, and/or device groups affected by the scripts;    -   (b) Testing operation and performance characteristics of scripts        and their associated virtual devices, device types, and/or        device groups; and/or    -   (c) Creating a library of scripts and associated virtual        devices, device types, and/or device groups;

(3) Providing the capability for entitled users to create, define, andtest virtual gateways, including:

-   -   (a) Defining the properties, associated values, and        communications/control protocols (e.g., BACnet, EnOcean,        Bluetooth Low Energy, etc.) for a particular virtual gateway        (e.g., Floor 1, Building 10, North Campus location);    -   (b) Defining the properties, associated values, and        communications/control protocols for a particular type of        virtual gateway (e.g., a specific model of gateway);    -   (c) Defining the properties, associated values, and        communications/control protocols for a group of virtual gateways        (e.g., Building 10, North Campus location);    -   (d) Assigning one or more virtual devices, device types, and/or        device groups to a virtual gateway, virtual gateway type, and/or        virtual gateway group;    -   (e) Removing one or more virtual devices, virtual device types,        and/or virtual device groups from a virtual gateway, virtual        gateway type, and/or virtual gateway group;    -   (f) Testing the operation, performance, loads for        communications/control protocols, processing, memory, and/or        data storage of virtual devices, virtual device types, and/or        virtual device groups assigned to virtual gateways, virtual        gateway types, and/or virtual gateway groups;    -   (g) Individually and/or collectively, assigning scripts and        associated virtual devices, virtual device types, and/or virtual        device groups to a virtual gateway to test the operation,        performance, loads communication/control protocols, processing,        memory, and/or data storage for the virtual devices, virtual        device types, and/or virtual device groups;    -   (h) Individually and/or collectively, assigning scripts and        associated virtual devices, virtual device types, and/or virtual        device groups to a virtual gateway type to test the operation,        performance, loads communication/control protocols, processing,        memory, and/or data storage for the virtual devices, virtual        device types, and/or virtual device groups;    -   (i) Individually and/or collectively, assigning scripts and        associated virtual devices, virtual device types, and/or virtual        device groups to a virtual gateway group to test the operation,        performance, loads communication/control protocols, processing,        memory, and/or data storage for the virtual devices, virtual        device types, and/or virtual device groups;    -   (j) Activating one or more scripts and associated virtual        devices, virtual device types, and/or virtual device groups for        a virtual gateway, virtual gateway type, and/or virtual gateway        group;    -   (k) Deactivating one or more scripts and associated virtual        devices, virtual device types, and/or virtual device groups for        a virtual gateway, virtual gateway type, and/or virtual gateway        group;    -   (l) Maintaining a library of active and inactive virtual        devices, virtual device types, and/or virtual device groups for        virtual gateways, virtual gateway types, and/or virtual gateway        groups;    -   (m) Maintaining a library of active/inactive, draft, verified,        and unverified scripts and associated virtual devices, virtual        device types, and/or virtual device groups for virtual gateways,        virtual gateway types, and/or virtual gateway groups; and    -   (n) Individually and/or collectively, assigning one or more        virtual gateways, virtual gateway types, and/or virtual gateway        groups to a computing environment to identify the resources        required and their performance in order to design, test,        finalize, implement, manage, and update the physical environment        required to efficiently support the M2M or IoT ecosystem;

(4) Enabling entitled users to select one or more physical gateways onwhich to implement a particular virtual gateway and its activescript(s), virtual device(s), virtual device type(s), and/or virtualdevice group(s). If the active script(s) to be implemented on thephysical gateway(s) reference virtual device(s), virtual device type(s),and/or virtual device group(s) and the physical gateway(s) are notcommunicatively connected to corresponding physical device(s), physicaldevice type(s), and/or physical device group(s), the activation of thevirtual device(s), virtual device type(s), and/or virtual devicegroup(s) may be suspended until communications are established betweenthe physical gateway(s) and the corresponding physical device(s),physical device type(s), and/or physical device group(s). Oncecommunication has been established, each of the physical device(s),physical device type(s), and/or physical device group(s) can besynchronized with its corresponding virtual device(s), virtual devicetype(s), and/or virtual device group(s), respectively. Suspension ofdevice(s), device type(s), and/or device group(s) will not affect theoperation of the implemented, active scripts:

-   -   (a) An entitled user can implement gateways using mirroring, in        which case all physical gateways that mirror a particular        virtual gateway will be automatically synchronized whenever that        virtual gateway is changed and/or whenever any physical gateway        within the set of mirrored physical gateways is changed; and    -   (b) An entitled user can implement gateways using copying, in        which case all physical gateways that implement a copy of a        virtual gateway will automatically be initialized according to        that virtual gateway as the source of configuration. In an        embodiment, for each copied physical gateway, an associated        mirrored virtual gateway is created. Changes that are activated        on either the copied virtual gateway or a physical gateway that        implements the copy will be synchronized between the two;

(5) Enabling entitled users to select one or more physical gateway typeson which to implement a virtual gateway type and its active script(s),virtual device(s), virtual device type(s), and/or virtual devicegroup(s):

-   -   (a) An entitled user can implement gateways using mirroring        based on type of gateway, in which case all physical gateway        that are of a type that mirrors a particular virtual gateway        type will be automatically synchronized whenever that virtual        gateway type is changed and/or whenever any physical gateway of        the mirrored type is changed; and    -   (b) An entitled user can implement gateways using copying based        on type of gateway, in which case all physical gateways that are        of a type that is a copy of a virtual gateway type will        automatically be initialized according to that virtual gateway        type as the source of configuration. In an embodiment, for each        physical gateway type, an associated mirrored virtual gateway        type is created. Changes that are activated on either the copied        virtual gateway type or a physical gateway that implements the        copied virtual gateway type will be synchronized between the        two;

(6) Enabling entitled users to select one or more physical gatewaygroups on which to implement a virtual gateway group and its activescript(s), virtual device(s), virtual device type(s), and/or virtualdevice group(s):

-   -   (a) An entitled user can implement gateways using mirroring        based on an associated group of gateways, in which case all        physical gateway that are in a group that mirrors a particular        virtual gateway group will be automatically synchronized        whenever that virtual gateway group is changed and/or whenever        any physical gateway in the group is changed; and    -   (b) An entitled user can implement gateways using copying based        on an associated group of gateway, in which case all physical        gateways that are in a group that is a copy of a virtual gateway        group will automatically be initialized according to that        virtual gateway group as the source of configuration. In an        embodiment, for each physical gateway group, an associated        mirrored virtual gateway group is created. Changes that are        activated on either the copied virtual gateway group or a        physical gateway that implements the copied virtual gateway        group will be synchronized between the two; and

(7) Enabling recovery:

-   -   (a) For physical gateways, physical gateway types, and/or        physical gateway groups that implement a copy of a virtual        gateway, virtual gateway type, and/or virtual gateway group:        -   (i) If the physical gateway, physical gateway type, and/or            physical gateway group goes offline due to a communications            issue, when it comes back online, it will automatically            synchronize with its associated virtual gateway, virtual            gateway type, and/or virtual gateway group, respectively;            and,        -   (ii) If the physical gateway, physical gateway type, and/or            physical gateway group goes offline due to system failure,            when it comes back online, it will automatically download            the most recently synchronized copy of its associated            virtual gateway, virtual gateway type, and/or virtual            gateway group, respectively; and    -   (b) For physical gateways, physical gateway types, and/or        physical gateway groups that mirror a virtual gateway, virtual        gateway type, and/or virtual gateway group, if the physical        gateway, physical gateway type, and/or physical gateway group        goes offline due to a communications issue or system failure,        when it comes back online, it will automatically synchronize        with its mirrored virtual gateway, virtual gateway type, and/or        virtual gateway group, respectively,

1. System Overview

1.1. Infrastructure

FIG. 1 illustrates an example system for the management of controlscripts and/or drivers, according to an embodiment. The system mayinclude a platform 110 comprising a set of one or more servers 112 whichhost and/or execute one or more of the various functions, processes,methods, and/or software modules described herein. It should beunderstood that platform 110 may comprise a cloud environment which mayor may not be dedicated to the disclosed gateway management processes.In a cloud environment, resources, such as virtual, logical, and/orphysical computing resources, storage resources, security resources,communications resource, management resources, and the like, may beshared and/or dedicated among services and applications.

In addition, platform 110 may be communicatively connected (e.g., viaone or more components, such as a communications resource of platform110) to one or more gateways 130 and/or one or more user systems 150 viaone or more network(s) 120 and may also be communicatively connected toone or more database(s) 114 (e.g., via one or more network(s), such asnetwork(s) 120 or a private network, or via a direct connection) and/ormay comprise one or more database(s) 114. Network(s) 120 may comprisethe Internet, and server(s) 112 may communicate with gateway(s) 130 anduser system(s) 150 through the Internet using standard transmissionprotocols, such as HyperText Transfer Protocol (HTTP), Secure HTTP(HTTPS), File Transfer Protocol (FTP), FTP Secure (FTPS), SSH FTP(SFTP), and the like, as well as proprietary protocols. It should alsobe understood that the components of platform 110 (e.g., cloudresources, such as server(s) 112) may be, but are not required to be,collocated. Furthermore, while platform 110 is illustrated as beingconnected to various systems through a single set of network(s) 120, itshould be understood that platform 110 may be connected to the varioussystems via different sets of one or more networks. It should also beunderstood that gateway(s) 130 and/or user system(s) 150 may compriseany type or types of computing devices capable of wired and/or wirelesscommunication, including without limitation, desktop computers, laptopcomputers, tablet computers, smart phones or other mobile phones,servers, game consoles, televisions, set-top boxes, electronic kiosks,Automated Teller Machines, Point-of-Sale (POS) terminals, intelligentwearable devices, medical or healthcare devices, any device within anIoT ecosystem, and the like. In addition, each gateway 130 may becommunicatively connected with one or more devices and/or other gateways130. While only a few gateways 130, devices 140, and user systems 130,one platform 110, one set of server(s) 112, and one set of database(s)114 are illustrated, it should be understood that the infrastructure maycomprise any number of gateway(s), device(s), user system(s),platform(s), sets of server(s), and database(s).

Platform 110 may comprise web servers that host one or more websites orweb services. In embodiments in which a website is provided, the websitemay comprise one or more user interfaces, including, for example,webpages generated in HyperText Markup Language (HTML) or other language(e.g., a graphical-based and/or text-based language). Platform 110transmits or serves these user interfaces in response to requests fromuser system(s) 150. It should be understood that user system(s) 150 maycomprise any type or types of computing devices capable of wired and/orwireless communication, including without limitation, desktop computers,laptop computers, tablet computers, smart phones or other mobile phones,servers, game consoles, televisions, set-top boxes, electronic kiosks,Automated Teller Machines, Point-of-Sale (POS) terminals, intelligentwearable devices, medical or healthcare devices, any device within anIoT ecosystem, and the like.

In some embodiments, these user interfaces may be served in the form ofa wizard, in which case two or more user interfaces may be served in asequential manner, and one or more of the sequential user interfaces maydepend on an interaction of the user or user system 150 with one or morepreceding user interfaces. The requests to platform 110 and theresponses from platform 110, including the user interfaces, may both becommunicated through network(s) 120, which may include the Internet,using standard communication protocols (e.g., HTTP, HTTPS). These userinterfaces or web pages may comprise a combination of content andelements, such as text, images, videos, animations, references (e.g.,hyperlinks), frames, inputs (e.g., textboxes, text areas, checkboxes,radio buttons, drop-down menus, buttons, forms, etc.), scripts (e.g.,JavaScript), and the like, including elements comprising or derived fromdata stored in one or more databases (e.g., database(s) 114) or devicesthat are locally and/or remotely accessible to platform 110. Platform110 may also respond to other requests from user system(s) 150.

Platform 110 may further comprise, be communicatively coupled with, orotherwise have access to one or more database(s) 114. For example,platform 110 may comprise one or more database servers that manage oneor more databases 114. A user system 150 or application executing onplatform 110 may submit data (e.g., user data, form data, etc.) to bestored in the database(s) 114, and/or request access to data stored insuch database(s) 114 (e.g., if requested by an entitled user). Anysuitable database may be utilized, including without limitation, anyrelational or non-relational database, datastore, data blob, and thelike, including cloud-based database instances and proprietarydatabases. Data may be sent to platform 110, for instance, using thewell-known POST request supported by HTTP, via FTP, other commonprotocols, proprietary protocols, etc. This data, as well as otherrequests, may be handled, for example, by cloud-side and/or server-sideweb technology, such as a servlet or other software module, executed byplatform 110. In addition, platform 110 may provide caching to speed upresponse times (e.g., for common requests).

In embodiments in which a web service is provided, platform 110 mayreceive requests from user system(s) 150, and provide responses ineXtensible Markup Language (XML) and/or any other suitable or desiredformat. In such embodiments, platform 110 may provide an applicationprogramming interface (API) which defines the manner in which usersystem(s) 150 may interact with the web service. Thus, user system(s)150, which may themselves be cloud environments and/or servers, candefine their own user interfaces, and rely on the web service toimplement or otherwise provide the backend processes, methods,functionality, storage, etc., described herein. For example, in such anembodiment, a client application executing on one or more user system(s)150 may interact with a server application executing on platform 110 toexecute one or more or a portion of one or more of the variousfunctions, processes, methods, and/or software modules described herein.The client application may be “thin,” in which case processing isprimarily carried out cloud-side and/or server-side by platform 110. Abasic example of a thin client application is a browser application,which simply requests, receives, and renders web pages at user system(s)150, while platform 110 is responsible for generating the web pages andmanaging database functions. Alternatively, the client application maybe “thick,” in which case processing is primarily carried outclient-side by user system(s) 150. It should be understood that theclient application may perform an amount of processing, relative toplatform 110, at any point along this spectrum between “thin” and“thick,” depending on the design goals of the particular implementation.In any case, the application, which may wholly reside on either platform110 or user system(s) 150 or be distributed between platform 110 anduser system(s) 150, can comprise one or more executable software modulesthat implement one or more of the processes, methods, or functions ofthe application(s) described herein.

1.2. Gateway Synchronization and Operation

While a gateway 130 may comprise any type of device capable ofcommunication with platform 110, in an embodiment, each gateway 130 is aproprietary device. Furthermore, in an embodiment, each gateway 130manages one or more communicatively connected (e.g., wireless or wired)devices 140.

FIG. 2 illustrates an example physical gateway 130 communicativelyconnected with platform 110, according to an embodiment. Gateway 130comprises script manager 132, script engine 134, and device manager 136.Platform 110 comprises a user interface module 116, synchronizationmodule 118, and has access to a virtual gateway 130′ (e.g., stored indatabase(s) 114 in platform 110 or another platform). It should beunderstood that there may be a plurality of virtual gateways 130′accessible to platform 110. Each virtual gateway 130′ may comprise avirtual representation of a physical gateway 130, including scriptmanager 132, script engine 134, device manager 136, and/or any othercontent or data stored and/or executed on physical gateway 130. A singlevirtual gateway 130′ may exist for individual physical gateways 130 orfor groups of two or more physical gateways 130 (which may beidentically-configured except for differences in the number and/oractivation of devices, device types, and/or device groups). For example,database(s) 114 may store associations between an identifier of avirtual gateway 130′ and the identifier(s) of one or more mirroredphysical gateway(s) 130 which are or should be synchronized with thatvirtual gateway 130′.

In an embodiment, when a physical gateway 130 is implemented by copyinga first virtual gateway 130′ onto the physical gateway, a unique, secondvirtual gateway is created for and associated with that physical gateway130 (e.g., via a stored association between the identifier of thephysical gateway 130 and the second virtual gateway in database(s) 114).It should be understood that this second virtual gateway may be a copyof the first virtual gateway 130′. Alternatively, the second virtualgateway may be created from scratch, rather than copied from apreexisting first virtual gateway. In either case, the second virtualgateway may be identical in structure to the first virtual gateway.However, when the second virtual gateway is copied from a first virtualgateway 130′, any wildcards in any scripts in the first virtual gateway130′ may be dereferenced in the second virtual gateway, in accordancewith the physical device(s), device type(s), and/or device group(s)communicatively connected to the associated physical gateway 130.Subsequently, any changes made to the second virtual gateway will bemirrored in the physical gateway 130, and any changes in the physicalgateway 130 will be mirrored in the second virtual gateway. Thus, thesecond virtual gateway, whether created from scratch or as a copy of thefirst virtual gateway 130′, operates in the same manner as first virtualgateway 130′, except that it is associated with, and specific to (e.g.,dereferenced with respect to), one particular physical gateway 130′,whereas the first virtual gateway 130′ is associated with, andgeneralized for, one or multiple physical gateways 130.

User interface module 116 on platform 110 provides a graphical userinterface for managing each gateway 130, virtual gateway 130′, or groupsof two or more physical gateways 130 and/or virtual gateways 130′ in auser's domain. In an embodiment, each virtual gateway 130′ and eachphysical gateway 130 associated with that virtual gateway 130′(including, for example, groups of mirrored physical gateways 130 thatare associated with a single virtual gateway 130′ or multiple virtualgateways 130′, for example, distributed across multiple platforms) ismanaged as a pair or collection. For instance, platform 110 may comprisea web server that serves web page(s) to user system(s) 150. These webpage(s) may comprise one or more inputs for creating, modifying (e.g.,editing a component, changing the status of a component, such as fromactive to inactive, etc.), and/or deleting components of gateway(s) 130.For example, the web page(s) may comprise inputs enabling a user tocreate, modify, or delete a script for one particular physical gateway130 and its associated virtual gateway 130′, or all physical gateways130 associated with a particular virtual gateway 130′ or multiplevirtual gateways 130′. As another example, the web page(s) may compriseinputs enabling a user to create, modify, or delete device information(e.g., device drivers, and/or definitions and/or configurations fordevices, device types, and/or device groups) for the device manager 136of one particular physical gateway 130 and its associated virtualgateway 130′, or all physical gateways 130 associated with a particularvirtual gateway 130′ or multiple virtual gateways 130′. In an embodimentdiscussed below, for each pair of mirrored gateways, synchronizationmodule 118 ensures that added, modified, or deleted scripts and/ordevice information are added, modified, or deleted, respectively, inboth the physical gateway(s) 130, as well as their associated virtualgateway(s) 130′.

In an embodiment, database(s) 114 comprises a master scripting libraryand/or a virtual gateway script library, either of which may compriseone or more master scripts available to users via user interface module116. Master scripts may comprise general scripts, tutorial scripts,scripts provided by a value-added reseller, licensed scripts, and/or thelike. For example, users may have access to a public set of scriptsand/or be able to purchase licenses for access to and use of variousscripts or groups of scripts within the master scripting library. Usersmay access scripts that are accessible to them (e.g., which they areentitled to access and/or modify) in the master scripting library andmodify them as needed to create scripts that support the users' needs orrequirements. Modified or unmodified scripts can then be copied ormirrored into physical gateway(s) 130 within their control (i.e., theiruser domain). For example, a user could select a previously-createdscript from the master scripting library, optionally modify the script,and download and activate the modified or unmodified script to gateway130 within the user's domain. In an embodiment discussed below,synchronization module 118 would download that activated script toscript manager 132 of corresponding physical gateway 130 as soon as aconnection to the physical gateway 130 is available. In an embodimentthat utilizes wildcards in scripts, if the activated script comprisesany wildcards, those wildcards would be dereferenced so as to bereplaced by an identifier of a corresponding physical device, physicaldevice type, and/or physical device group communicatively connected tophysical gateway 130.

Synchronization module 118 on platform 110 provides synchronizationbetween virtual gateway 130′ and physical gateway(s) 130. As discussedabove, there may be one-to-one correspondence between one virtualgateway 130′ and one physical gateway 130. For example, in the eventthat a virtual gateway 130′ is copied to a particular physical gateway130, that virtual gateway 130′ may be copied, any wildcards in itsscripts may be dereferenced, and the copy of the virtual gateway 130′may be uniquely associated with the particular physical gateway 130 inone-to-one correspondence. Additionally, there may be one-to-manycorrespondence between one virtual gateway 130′ and a plurality ofphysical gateways 130, or many-to-one or many-to-many correspondencebetween multiple virtual gateways 130′ and one or more physical gateways130. This may occur, for example, when a group of physical gateways 130is selected to be mirrored to a particular virtual gateway 130′ ormultiple virtual gateways 130′. However, it should be understood that asingle physical gateway 130 may be mirrored to a particular virtualgateway 130′, resulting in a one-to-one correspondence, similar to theone-to-one correspondence resulting from a virtual gateway 130′ beingcopied to a physical gateway 130. In an embodiment, the only differencemay be that, when a virtual gateway 130′ is copied to a physical gateway130, any scripts in the copy of the virtual gateway 130′ on platform 110are dereferenced with respect to the physical gateway 130, whereas, whena physical gateway 130 is mirrored to virtual gateway(s) 130′, thescripts of virtual gateway(s) 130′ on platform(s) 110 are notdereferenced. In the latter case, when the physical gateway 130 that ismirrored to the virtual gateway(s) 130′ is synchronized with the virtualgateway(s) 130′, any downloaded scripts may be dereferenced at thephysical gateway 130 (or at platform 110 prior to being downloaded tophysical gateway 130), while the scripts in the virtual gateway(s) 130′on platform 110 may continue to include any wildcards. Thus, thesynchronization performed by synchronization module 118 may be the same,regardless of the nature of virtual gateway 130′, but it should beunderstood that scripts may need to be dereferenced (e.g., bysynchronization module 118 or another module, such as script manager 132or script engine 134) when the virtual gateway 130′ comprises wildcards.Accordingly, regardless of the nature of virtual gateway 130′,synchronization between that virtual gateway 130′ and its one ormultiple associated physical gateways 130 may be referred to herein as“mirroring,” and those associated physical gateways 130 may be referredto herein as “mirrored gateways” or “mirrored physical gateways.”

In an embodiment, synchronization is performed automatically whenever achange is made to one of the modules to be synchronized (e.g., scriptmanager 132, script engine 134, and/or device manager 136) in eithervirtual gateway 130′ and/or any physical gateway(s) 130 that areassociated with virtual gateway(s) 130′. For example, if a script ismodified in the script manager of a virtual gateway 130′ (e.g., via userinterface module 116), synchronization module 118 may automaticallydownload or modify the corresponding script in script manager 132 of anyassociated physical gateway(s) 130. Similarly, if a device driver,virtual device, virtual device type, and/or virtual device group isadded to the device manager of a virtual gateway 130′, synchronizationmodule 118 may automatically add the device driver, correspondingphysical device, corresponding physical device type, and/orcorresponding physical device group, respectively, to device manager 136of any associated physical gateway(s) 130.

Synchronization module 118 may continuously synchronize with eachmirrored gateway 130 as long as a connection 210 exists between platform110 and the gateway 130. If a connection between platform 110 and amirrored gateway 130 is lost, synchronization module 118 may performsynchronization as soon as connection 210 between platform 110 andmirrored gateway 130 can be reestablished. In this case, the virtualgateway 130′ associated with the mirrored gateway 130, for which aconnection 210 is not currently established, acts as a container whichsaves the configuration of physical gateway 130 to be implemented bysynchronization module 118 as soon as connection 210 is established. Inalternative or additional embodiments, synchronization may be performedmanually (e.g., in response to a user operation) and/orsemi-automatically (e.g., following user confirmation in response to aprompt).

It should be understood that, while FIG. 2 illustrates the virtualgateway 130′ as comprising virtual representations of the script manager132, script engine 134, and device manager 136 of associated mirroredphysical gateway 130, the virtual gateway 130′ may comprise virtualrepresentations of more or fewer components of mirrored physical gateway130, depending on which elements are needed to be synchronized withinthe given design. For example, in an embodiment, only the active scriptsand/or device information (e.g., device drivers, and/or definitionsand/or configurations for devices, device types, and/or device groups)may be synchronized between virtual gateway 130′ and mirrored physicalgateway 130. In such an embodiment, virtual gateway 130′ only needs tocomprise a list of scripts, virtual devices, virtual device types,virtual device groups, and/or device drivers to be synchronized with thecorresponding active scripts, physical devices, physical device types,physical device groups, and/or device drivers stored locally on theassociated mirrored physical gateway 130. In embodiments, in which thevirtual gateways 130′ are themselves executable (e.g., in the cloud), acommon or shared script engine may be utilized to execute scripts frommultiple virtual gateways 130′ at platform 110.

Script manager 132 on physical gateway 130 manages scripts forcontrolling one or more physical devices 140, physical device types,and/or physical device groups communicatively connected to mirroredphysical gateway 130. In an embodiment, script manager 132 stores theactive scripts in a local database in a memory on physical gateway 130.Script manager 132 may subscribe to platform 110 (i.e., be mirrored to avirtual gateway 130′ on platform 110), such that synchronization module118 maintains synchronization between at least a subset of activescripts from the virtual gateway 130′, associated with physicalgateway(s) 130, and the scripts stored locally in the memory of physicalgateway(s) 130. Thus, whenever an active script is added to virtualgateway 130′, synchronization module 118 also transfers that script toscript manager 132 of each mirrored physical gateway 130 viaconnection(s) 210, such that the script is stored both locally on eachmirrored physical gateway 130 and remotely in virtual gateway(s) 130′.Likewise, whenever a script is deleted or deactivated from virtualgateway 130′, synchronization module 118 also requests deletion ordeactivation of that script from script manager 132 of each mirroredphysical gateway 130 via connection(s) 210, such that the script isdeleted from both virtual gateway(s) 130′ and physical gateway(s) 130.In addition, whenever an active script is modified in virtual gateway130′, synchronization module 118 communicates with script manager 132 ofeach mirrored physical gateway 130 via connection(s) 210, in order toimplement the same modifications to the locally-stored copy of thescript on physical gateway(s) 130 (e.g., by replacing the local scriptor by applying a delta representing the incremental modification to thelocal script). It should be understood that, in a similar manner,synchronization module 118 may effect changes in virtual gateway 130′ inorder to synchronize virtual gateway 130′ with modifications to orchanges at its associated mirrored physical gateway(s) 130.

In an embodiment, synchronization module 118 synchronizes only activeand/or verified scripts in virtual gateway 130′ with scripts stored onmirrored physical gateway(s) 130. For example, scripts in virtualgateway 130′ may be associated with a status of “active” or “inactive.”An “inactive” status indicates that the script should not be executed invirtual gateway 130′ and its associated mirrored physical gateway(s)130, whereas an “active” status indicates that the script should beexecuted in virtual gateway 130′ and its associated mirrored physicalgateway(s) 130. When synchronizing scripts from virtual gateway 130′ toits associated mirrored physical gateway(s) 130, synchronization module118 may refrain from synchronizing any scripts with an “inactive” statusto mirrored physical gateway(s) 130. Alternatively, synchronizationmodule 118 may add the inactive script to mirrored physical gateway(s)130, but with its “inactive” status. In addition, if a script in virtualgateway 130′ is changed from “active” to “inactive,” synchronizationmodule 118 may either change the status of the script to “inactive” inmirrored physical gateway(s) 130 or delete the script from mirroredphysical gateway(s) 130.

Synchronization module 118 may treat verified and unverified scripts ina similar manner. Verified scripts are those that have been verified tooperate in the intended manner, whereas unverified scripts are thosethat have not been verified to operate in the intended manner. Forexample, unverified scripts may comprise incomplete and/or untestedscripts, which are still in the process of being developed or debugged.In an embodiment, synchronization module 118 does not mirror unverifiedscripts from virtual gateway 130′ to mirrored physical gateway(s) 130.Alternatively, a user may specify whether or not unverified scriptsshould be mirrored on physical gateway(s) 130 (e.g., by setting thestatus of the script to “active” or “inactive,” as described above).

In an embodiment, script manager 132 on physical gateway 130 provideslocally-stored scripts as inputs to script engine 134. Script engine 134may comprise a virtual machine that executes input scripts. In anembodiment, physical gateway 130 may also comprise a compiler interposedbetween, or comprised within one of, script manager 132 and scriptengine 134. In such an embodiment, scripts stored on physical gateway130 may be stored as source code, that is fed through the compiler, andoutput as virtual machine code to be executed by the virtual machine ofscript engine 134. In an embodiment, the virtual machine of scriptengine 134 provides threaded execution of multiple scripts in parallel.

In an embodiment, script engine 134 interfaces with device manager 136,which in turn interfaces with device(s) 140 via wired and/or wirelessconnections. Device manager 136 may comprise one or more drivers forcommunicating and interacting with device(s) 140, device types, and/ordevice groups. Device(s) 140 may comprise virtually any type or groupand combination of types or groups of devices, including withoutlimitation, sensors (e.g., motion sensors, temperature sensors, humiditysensors, barometers, open/closed sensors, locked/unlocked sensors,etc.), locks (e.g., door or window locks), doors, windows, lights,heating, ventilation, and air conditioning units (HVACs), vendingmachines, automatic teller machines (ATMs), point-of-sale (POS)terminals, security systems and components, irrigation systems andcomponents, pools or spas, faucets, appliances (e.g., stove,refrigerator, washing machine, etc.), electrical systems and components,gas systems, printers, televisions, speakers, gates, boilers, heatingsystems, chillers, refrigeration systems, medical or healthcarewearables and systems, etc. Device manager 136 may communicate withdevice(s) 140 using wired communication (e.g., via physical ports ingateway 130) and/or wireless communication (e.g., BACnet, Modbus,LonWorks, EnOcean, Bluetooth Low Energy (BLE), Wi-Fi, such as 802.11a/b/g/n/ac, Wi-Fi Low Energy, Z-Wave, ZigBee™, Bluetooth™, near-fieldcommunication (NFC), ANT, GPIO, industry standard or proprietaryprotocols, etc.). In an embodiment, gateway 130 comprises one or moretransceivers (e.g., antennas) providing gateway 130 with the ability tocommunicate via one or more wireless technologies.

Device information ((e.g., device drivers, and/or definitions and/orconfigurations for devices, device types, and/or device groups) may beadded, modified, and/or removed from device manager 136, as needed,depending on the device(s) 140, device types, and/or device groups withwhich a physical gateway 130 needs to communicate. For example, a firstdevice driver may be added to device manager 136 for communication withand management of a first device, and a second device driver may beadded to device manager 136 for communication with and management of asecond, different device. The same can be said for different devicetypes and device groups. In addition, device information may be removedfrom device manager 136, when they are no longer needed (e.g., whengateway 130 no longer needs to communicate with a certain device, devicetype, or device group).

Device information may be implemented as plug-in software modules todevice manager 136, such that each device, device type, device group,and device driver can be easily added, modified, and/or removed fromdevice manager 136 when needed. Advantageously, this enables thefeatures and support of the system (i.e., gateways 130 and platform 110)to be separated from the features and support of the individualdevice(s) 140, device type(s), and device group(s). In other words, newfeatures to the system (and technical support for those and olderfeatures) do not affect device(s) 140, device type(s), and devicegroup(s), since older configurations (e.g., drivers) may be maintainedfor those device(s), device type(s), and device group(s). Conversely,new features to device(s) 140, device type(s), and device group(s) (andtechnical support for those and older features) do not affect thesystem, since the older configurations may continue to properly operatewith the affected devices, device type(s), and device group(s) or elsethe old configurations can be easily replaced with newer configurations(i.e., by plugging in new devices, device types, device groups, and/ordevice drivers to device manager 136 in place of or in addition to theold devices, device types, device groups, and/or device drivers).

As discussed above, device information (e.g., device drivers, and/ordefinitions and/or configurations for devices, device types, and/ordevice groups) in device manager 136 may be synchronized with the deviceinformation in the device manager of virtual gateway 130′ viasynchronization module 118. Thus, if device information is added tophysical gateway 130, that device information is also added to theassociated virtual gateway 130′, and vice versa. Similarly to scripts,device information may be associated with statuses, such as “inactive”or “active” (e.g., a definition and/or configuration of a particulardevice, device type, and/or device group may be set to “inactive” or“active”), and synchronization module 118 may synchronize deviceinformation in device manager 136 of physical gateway 130 with deviceinformation in the device manager of virtual gateway 130′ in accordancewith those statuses.

Device manager 136 provides an interface to receive data from one ormore device(s) 140, device types, and device groups and/or send data toone or more device(s) 140, device types, and device groups. For example,device manager 136 may receive sensor data from a sensor device 140(e.g., a temperature measurement from a temperature sensor, a binaryvalue from an open/closed sensor, the status of a switch, a valuerepresenting the detection of motion from a motion sensor, etc.). Inaddition, device manager 136 may send instructions or commands to anoperable device 140 (e.g., a command to a locking device to open orclose a deadbolt on a door, a command to a lighting device to turn on oroff a floodlight, etc.), device type (e.g., change the temperature onall thermostats), or device group (e.g., reset values for all devicesand device types in an HVAC system). Data received by device manager 136from device(s) 140, device types, and device groups may be provided asinputs to one or more active scripts executing on script engine 134,whereas outputs of one or more active scripts executing on script engine134 may be sent as or converted into instructions, commands, or otherdata to one or more devices 140, device types, and device groups bydevice manager 136. In this manner, the active script(s) executing onscript engine 134 (e.g., multiple active scripts executing as parallelthreads) may control and/or react to active device(s) 140, device types,and device groups.

In an embodiment, device manager 136 detects unavailable and/or missingdevices, device types, and device groups. For example, device manager136 may implement a conventional heartbeat feature or other method ofdetecting the loss of a communicative connection for each device 140,device type, and/or device group. In the event that device manager 136detects that a device, device type, and/or device group, with which itis supposed to and/or has previously had a connection, is no longerconnected (e.g., after a predetermined number of attempts atestablishing a connection or after a predetermined duration ofconnection loss), the device manager 136 may execute error processing,which may include generating an alert (e.g., a user interface message,email message, text message, etc.) to notify one or more recipients ofthe failure.

1.3. Utilization of Virtual Gateways

As a consequence of the synchronization process described above, eachmirrored physical gateway 130 is associated with a virtual gateway 130′at platform 110 (e.g., stored in database(s) 114 and operated on byplatform 110), or multiple virtual gateways 130′ that may beinstantiated on one or more platforms 110. In instances in which thereare no connection failures, the virtual gateway(s) 130′ associated withmirrored gateway(s) 130 will accurately reflect the currentconfiguration of each mirrored gateway 130. For example, the virtualgateway(s) 130′ will at least identify each script and deviceinformation (e.g., device drivers, and/or definitions and/orconfigurations for devices, device types, and/or device groups) that isactive on the associated mirrored gateway(s) 130. In instances in whichthere are connection failures, the virtual gateway(s) 130′ may notaccurately mirror the current configuration of its associated mirroredgateway(s) 130, but such inaccuracies are temporary and will be resolvedonce connection(s) with the associated mirrored gateway(s) 130 areestablished. The accurate, continually-updated nature of the virtualgateway(s) 130′ provides several utilization opportunities.

1.3.1. Backup and Restore

Since each virtual gateway 130′ mirrors its associated physicalgateway(s) 130, the virtual gateways 130′ can be used as a backup fortheir associated mirrored physical gateways 130 in the event of afailure. Specifically, in the event that a mirrored physical gateway 130experiences a failure or is replaced with a new physical gateway 130(e.g., via a hot swap), the virtual gateway 130′ associated with thatmirrored physical gateway 130 can be used to restore the recovered orreplacement gateway 130 to the proper, up-to-date configuration. Thisbackup and restoration process can be automatic, semi-automatic, ormanual. It should be understood that functions of the backup andrestoration process can be performed and/or set through graphical userinterfaces provided by user interface module 116 of platform 110.

1.3.2. Snapshots

In addition, one or more virtual gateways 130′ can be stored as asnapshot or restore point for its associated mirrored gateway(s) 130.For instance, a given physical gateway 130 or group of physical gateways130 may be associated with a plurality of virtual gateways 130′, eachrepresenting the configuration of that physical gateway 130 or group ofphysical gateways 130 at a different point in time (e.g., including oneor more past times as well as the current time). Thus, the configurationof the physical gateway 130 could be restored to any point in timerepresented by one of the plurality of associated virtual gateways 130′.It should be understood that functions of the snapshot process can beperformed and/or set through graphical user interfaces provided by theuser interface module 116 of platform 110.

1.3.3. Cloud-Based Gateways

Another consequence of the synchronized virtual gateways 130′ is thatexecution of active scripts and/or device drivers and/or management ofactive devices, device types, and/or device drivers for a given physicalgateway 130 can be offloaded to platform 110. For instance, in anembodiment in which platform 110 is a cloud platform (i.e., a public orprivate platform utilizing shared or private virtual and/or physicalresources), execution of active scripts and/or device drivers and/ormanagement of active devices, device types, and/or device drivers for agiven physical gateway 130 can be performed “in the cloud.” In such anembodiment, the physical gateway 130 may simply provide an electronicinterface to device(s) 140, device types, and device groups, whilecontrol processing is performed by a script engine on platform 110and/or communications with device(s) 140, device types, and devicegroups are managed by a device manager on platform 110. For example,this may be useful in the implementation of a thin gateway 130, or ifthere is an internal failure in the physical gateway 130 that does notaffect its ability to communicate with device(s) 140. In the case ofsuch a failure, a recovery module in platform 110 may automaticallyswitch or initiate switching of the physical gateway 130 to a thingateway in which script execution and/or device management is offloadedto platform 110.

In an embodiment, a user may specify that one or more functions ofcertain physical gateways 130 should be performed in the cloud usingtheir associated virtual gateway(s) 130′. It should be understood that,in this case, physical gateways 130 can be initialized from the start ascloud-based gateways, in which one or more of their functions arecloud-based (i.e., performed by associated virtual gateway(s) 130′).

1.3.4. Initialization

Furthermore, virtual gateway(s) 130′ can be used to quickly configure orinitialize new physical gateway(s) 130 (e.g., newly purchased gateways,gateways recovered from a loss of power, hardware failure, etc.).Specifically, in the case that a new gateway is to be configured in thesame manner as a previously-configured gateway 130, the new gateway cansimply be synchronized with the virtual gateway 130′ associated withthat previously-configured gateway 130 or added to a type or group ofgateways that is automatically and continuously synchronized with thevirtual gateway 130′ by synchronization module 118. Alternatively, thatvirtual gateway 130′ can be copied to the new physical gateway 130 togenerate a new (e.g., dereferenced) copy of the virtual gateway 130′(e.g., at platform 110) that is uniquely associated with the newphysical gateway 130. In this case, the new copy of the virtual gateway130′ may be automatically and continuously synchronized with the newphysical gateway 130.

1.3.5. Gateway Web Portal

In addition, in an embodiment, virtual gateway 130′ in conjunction withuser interface module 116 on platform 110 may act as a web portal to theassociated physical gateway(s) 130. Specifically, a graphical userinterface, constructed based on a virtual gateway 130′, can be used by auser to manage the virtual gateway 130′ (e.g., edit the virtual gateway130′). Since changes in the managed virtual gateway 130′ aresynchronized (e.g., automatically and continuously synchronized) withits associated mirrored physical gateway(s) 130 by synchronizationmodule 118, management of the virtual gateway 130′ is also management ofthe associated mirrored physical gateway(s) 130. In other words, sincechanges in the virtual gateway 130′ are replicated in its associatedmirrored physical gateway(s) 130, the virtual gateway 130′ and itsassociated mirrored physical gateway(s) 130 are managed simultaneouslyby a user through management of the virtual gateway 130′ via userinterface module 116. However, it should be understood that in analternative or additional embodiment, user interface module 116 onplatform 110 may simply act in conjunction with each mirrored physicalgateway 130 to generate a web portal for the physical gateway (e.g., byquerying each gateway 130 for its status and/or configuration, anddynamically generating a graphical user interface from the queryresults).

In an embodiment, the graphical user interface for managing the virtualgateway 130′ and its associated mirrored gateway(s) 130 may comprise auser-friendly point-and-click or touch interface. For example, a usercan add, edit (e.g., activated/deactivated, modified, etc.), and/ordelete scripts on mirrored physical gateway(s) 130 via a simplepoint-and-click operation or touch operation (e.g., for a user system150 that is touch-enabled). For example, the graphical user interfacemay enable a user with the appropriate entitlement to easily selectscript(s) from a list of scripts (e.g., stored in a similar manner tothe master scripting library in database(s) 114 of platform 110) to beadded to the associated mirrored gateway(s) 130 associated with aparticular virtual gateway 130′. In addition, the graphical userinterface may enable an entitled user to easily select script(s) from alist of scripts in the virtual gateway 130′ to be removed, edited,verified, activated, and/or deactivated. The graphical user interfacemay also allow enable an entitled user to select script(s) from a listof scripts in a first virtual gateway 130′ and mirror or copy the scriptto a second, different virtual gateway 130′. As discussed above, anychanges to a virtual gateway 130′ will be reflected in all of itsassociated mirrored gateway(s) 130 with which synchronization module 118can establish a connection 210.

In an embodiment, the graphical user interface enables an entitled userto select and mirror or copy scripts and/or device information (e.g.,device drivers, and/or definitions and/or configurations for devices,device types, and/or device groups) stored in a source (e.g., a virtualgateway 130′ and/or a physical gateway 130) from the source to one ormore targets (e.g., another virtual gateway 130′ and/or a physicalgateway 130). For example, an entitled user may select a virtual gateway130′, and select one or more physical gateway(s) 130 to which theselected virtual gateway 130′ is mirrored or copied. In a similarmanner, an entitled user can select device information, and select oneor more physical gateway(s) 130 to which the selected device informationis mirrored or copied.

It should be understood that the gateway web portal may be available forall virtual and/or physical gateway(s) to which a user is entitled viaplatform 110. The gateway web portal may comprise a graphical userinterface that enables an entitled user to access (e.g., edit) multiplemirrored virtual and/or physical gateways at once (e.g., all gatewaysand/or a subset or grouping of gateways within the user's domain) and/ormay comprise a graphical user interface which enables a user to accessmirrored virtual and/or physical gateways individually.

1.4. Script Editor

In an embodiment, user interface module 116 of platform 110 provides agraphical user interface (i.e., a script editor) to a user for creatingand editing scripts stored in a library of scripts (e.g., the masterscripting library and/or gateway script library discussed above) and/oron virtual gateways 130′ and physical gateways 130. As discussedelsewhere herein, scripts may be edited at one or more points duringgateway management (e.g., by entitled users on gateway(s) within thoseusers' domains, on authorized and authenticated devices, etc.). Forinstance, a script may be selected for editing from a master scriptinglibrary and/or from a list of scripts stored in a virtual gateway 130′or physical gateway 130.

As one example, in response to an entitled user selecting an identifierof a particular physical gateway from a graphical user interface, userinterface module 116 may provide the user with a list of scripts storedon the selected physical gateway. Then, in response to the userselecting an identifier of a particular script from the list of scripts,user interface module 116 may provide the user with a user interface forthe script editor. Once the user indicates in the script editor thatediting of the script has been completed (e.g., by operating a “save”icon or button in the script editor to save the script, whether completeor incomplete, verified or unverified, active or inactive), userinterface module 116 may return the user to the list of scripts storedon the selected physical gateway.

In an embodiment, the script editor enables an entitled user toconstruct scripts by graphically piecing various script componentstogether semantically and syntactically. For example, the scriptcomponents may include, without limitation, triggers, conditions,devices, device attributes or properties, actions, and the like. Thescript editor may comprise an interactive interface that enables theuser to graphically, semantically and syntactically, place and connectthese components in a logical manner. The script editor may check forcorrect semantics and syntax during and/or after editing. If the scriptis incorrect semantically and/or syntactically, the script editor mayhighlight the errors for the user to correct. In addition, the scripteditor may prohibit the user from saving the script as complete and/oractivating the script. Furthermore, the script editor may convert theuser-constructed components into an underlying standard or proprietaryscripting language (e.g., during editing, after the script has beensaved, after the script has been activated, after the script has beenverified for correct semantics and syntax, etc.). Alternatively oradditionally, the script editor may enable the user to simply write ascript directly using the underlying scripting language. In either case,the underlying scripting language may be compiled into code (e.g.,virtual-machine code, bytecode, or binary code) for execution by scriptengine 134.

The script editor may enable an entitled user to change individualcomponents of a script, for example, by changing a particular condition,trigger, or device. The script editor may also enable the user to mirroror copy a script to be used as a template or starting point for a newscript. Furthermore, the script editor may enable the user to renamescripts, change the status of a script (e.g., activate or deactivate ascript), manually synchronize a virtual gateway 130′ with its associatedphysical gateway(s) 130, and/or automatically, semi-automatically,and/or manually mirror or copy scripts among virtual gateway(s) 130′and/or physical gateway(s) 130.

In an embodiment, when the user is editing a particular script stored ina virtual or physical gateway, the script editor may request dynamicchanges from the device manager of the gateway. For instance, if a useris editing a particular script stored on a physical gateway 130, deviceidentifier(s) for all device(s) 140, device types, and/or device groupscommunicatively connected to the physical gateway may be retrieved byplatform 110 (e.g., by querying device manager 136 or other module ofphysical gateway 130). These device, device type, and/or device groupidentifier(s) may then be available in the script editor for userselection where appropriate. For example, if a user adds or is editing aparticular script component in the script and the particular scriptcomponent references a particular device, a drop-down menu that includesall of the available device, device type, and/or device groupidentifier(s) or a subset of device identifier(s) for devices, devicetypes, and/or device groups that are appropriate for the given scriptcomponent (e.g., sensors for a condition component) may be provided,such that the user may select the appropriate device, device type, ordevice group identifier to be referenced in the script component. Inembodiments that use wildcards, a wildcard version of the deviceidentifier(s) may be made automatically or manually available and/orselectable. For example, specific device, device type, and device groupidentifier(s) available at the gateway may be converted into regularexpressions or otherwise made generic so that they cover a particulartype or types of device and/or group or groups of devices (e.g., in awildcard format, described in more detail elsewhere herein), instead ofonly covering the particular physical device communicatively connectedto the particular gateway.

In an embodiment, the script editor may comprise diagnostic and/ordebugging tools. Thus, a script can automatically or manually (e.g., bythe user) be evaluated and debugged (e.g., verified) prior to activation(e.g., by checking whether or not the script is semantically and/orsyntactically correct), or to address issues that are identified afteractivation. It should be understood that verifying the script, which maybe executed after debugging, may verify operation of the script againstthe wildcards and/or physical devices, physical device types, and/orphysical device groups that are encompassed in the script, may verifythe script across all of the gateways on which the script is active, andmay provide group diagnostic and debugging information for the entiregroup of affected gateways.

The script editor may also manage and/or enforce version control forscripts. For example, each incremental modification to a script may beautomatically, semi-automatically, and/or manually stored as a newversion of the script, and each older version of the script may bemaintained in storage for future viewing, reference, roll-back, etc.This version control may be performed for both mirrored and copiedscripts.

1.5. Script Wildcards

In an embodiment, one or more wildcards may be used to representdevice(s) 140, device type(s), and/or device group(s) in the abstractduring the creation or editing of a script (e.g., in the script editordiscussed above). A wildcard enables the script to reference a type ortypes of device (e.g., particular model of thermostat) and/or group orgroups of devices (e.g., components of an HVAC system) without beingbound to a particular device. A wildcard may take any form (e.g., anasterisk, period, etc.) that is capable of providing a generic devicename representing type(s) of devices and/or group(s) of devices.

By using wildcards to reference devices, device types, and/or devicegroups in a script, the script can be generalized for a plurality ofgateways. Thus, in an embodiment, one or more or all of the scripts inthe master scripting library may comprise wildcards to representdevices, device types, and/or device groups referenced in the script(s).These wildcards may be maintained in scripts that are added to virtualgateways 130′. Alternatively, the wildcards may be dereferenced whenadded to virtual gateways 130′. This dereferencing within a virtualgateway 130′ may be useful when the virtual gateway 130′ is associatedwith only a single physical gateway 130 or is associated with multiplephysical gateways 130 that are communicatively connected toidentically-named sets of device(s) 140.

When a script is locally stored onto a physical gateway 130 (e.g., viasynchronization module 118) or compiled (e.g., by script manager 132 orscript engine 134), any wildcards in the script may be dereferenced(i.e., if not already dereferenced). In other words, the script willassume the properties of the specific devices corresponding to thedevice(s), device type(s), and/or device group(s) referenced by thewildcards. For instance, each wildcard may be replaced with a specificdevice identifier (e.g., device number or device name) of a device 140,device type, or device group that is communicatively connected togateway 130 (e.g., via device manager 136) and satisfies the wildcard.

As a non-limiting example, a script in the master scripting library mayreference a device “frontdoorswitch*”. In this case, the wildcard is anasterisk “*”. Thus, the reference “frontdoorswitch*” genericallyrepresents any front door switch within device(s) 140. When the scriptis implemented on a physical gateway 130, this wildcard is dereferenced(e.g., at the physical gateway 130 on which it is to be executed) bybeing automatically replaced by designators or other properties of oneor more particular physical device(s) 140 communicatively available tothe gateway 130 and associated with the wildcard “frontdoorswitch*”. Theproperty values of each particular device(s) 140 may then be configuredconsistent with the wildcard-defined property values for scriptexecution on the physical gateway 130.

In an embodiment, if a device identifier in a list of device(s) 140,device types, or device groups available to a physical gateway 130matches the reference “frontdoorswitch*”, the reference“frontdoorswitch*” is replaced in the script to be executed on thephysical gateway 130 with that device identifier. For example, if thelist of device identifiers comprises the device identifier“frontdoorswitch01”, this device identifier is matched to the reference“frontdoorswitch*” and substituted into the script (e.g., prior tocompilation of the script into virtual-machine code) in place of thereference “frontdoorswitch*”. Consequently, the dereferenced script willreference identifier(s) for particular device(s), rather than genericdevice(s) represented by wildcards.

1.6. Script Mirroring

FIG. 3 illustrates a script mirroring module 119 of platform 110,according to an embodiment. In this embodiment, an entitled user withcontrol over one or more mirrored gateways 130 (e.g., 130-1, 130-2, . .. 130-N) may access a graphical user interface (e.g., web page(s)) viauser interface module 116 of platform 110 (e.g., using a user system150). The graphical user interface may comprise one or more inputs forselecting or otherwise identifying a script and one or more inputs forselecting or otherwise identifying a virtual gateway 130′ or a group ofmultiple virtual gateways 130′ and/or a physical gateway 130 and/orgroup of multiple gateways 130. The graphical user interface may alsocomprise one or more inputs for receiving an indication from the user to“mirror” the identified script to the identified gateway or group ofgateways. Script mirroring comprises sending the identified script toeach identified virtual and/or physical gateway. In the case that one ormore physical gateways are identified, the script is transmitted to thephysical gateway(s) over a connection 210 (e.g., 210-1, 210-2, . . .210-N). For example, script mirroring module 119 may request the scriptmanager 132 of each identified gateway 130 to store a local mirror(e.g., copy) of the script to be executed by the gateway's respectivescript engine 134.

In addition, script mirroring module 119 may add the identified scriptto the virtual gateway(s) 130′ associated with each identified physicalgateway 130. In other words, all virtual gateway(s) 130′ associated witha physical gateway 130 are updated to account for the new scriptmirrored to the physical gateway 130. As noted above, there may be adiscrete virtual gateway 130′ associated with each physical gateway 130,or there may be a single virtual gateway 130′ associated with multiplemirrored (e.g., identically-configured) physical gateways 130.

As an example, an entitled user may select an identifier of a scriptfrom the master scripting library discussed above or from a set ofuser-created scripts. The user may then select an identifier of avirtual or physical gateway, identifiers of multiple virtual or physicalgateways, and/or an identifier of a group comprising multiple virtual orphysical gateways. In the illustrated example, the group of multiplephysical gateways comprises gateways 130-1 to 130-N. When the userperforms an operation (e.g., selecting an icon or button) indicatingthat the identified script should be “mirrored” to the identifiedphysical gateways 130-1 to 130-N, script mirroring module 119 transfersa mirror of the identified script to each of the gateways 130-1 to 130-Nover their respective connections 210-1 to 210-N. In other words, theidentified script is stored locally at each of physical gateways 130-1to 130-N. If a mirror of the current version of the identified script isalready stored at one of the identified gateways, transfer of the mirrormay be selectively skipped or the stored mirror may be overwritten. Inaddition, in embodiments which utilize the virtual gateway 130′described above, the identified script may be added to the virtualgateway(s) 130′ associated with the physical gateway(s) 130-1 to 130-N.

When a script comprising wildcards is mirrored to one or more physicalgateways 130, each wildcard in the script is dereferenced at eachgateway 130, so as to be automatically replaced with particulardevice(s) 140, as discussed elsewhere herein. Accordingly, a script withgeneric device, device type, and/or device group references can bemirrored to a plurality of gateways 130, and the generic deviceidentifier(s) in the mirrored script are automatically replaced withspecific identifiers for the specific devices, device types, and/ordevice groups connected to each respective physical gateway 130.

2. Process Overview

Embodiments of processes for managing control scripts for physicalgateways will now be described in detail. It should be understood thatthe described processes may be embodied in one or more software modulesthat are executed by one or more hardware processors, which may beexecuted wholly by processor(s) of platform 110, wholly by processor(s)of gateway(s) 130 and/or user system(s) 150, or may be distributedacross platform 110 and gateway(s) 130 and/or user system(s) 150 suchthat some portions or modules of the application are executed byplatform 110 and other portions or modules of the application areexecuted by gateway(s) 130 and/or user system(s) 150. The describedprocess may implemented as instructions represented in source code,object code, and/or machine code. These instructions may be executeddirectly by the hardware processor(s), or alternatively, may be executedby a virtual machine operating between object code and the hardwareprocessors. In addition, the disclosed application may be built upon orinterfaced with one or more existing systems.

2.1. Gateway Editing

FIG. 4 illustrates a process 400 for editing a gateway 130, according toan embodiment. In step 410, a user interface is provided to a user foradding, modifying (e.g., changing components of a script or othercomponent, changing a status of a script or other component, such asactivating or deactivating the script), and/or deleting one or morescripts, device information (e.g., device drivers, and/or definitionsand/or configurations for devices, device types, and/or device groups),and/or other changeable components of a gateway. For example, this userinterface may be provided by user interface module 116 of platform 110.The user interface may be provided for editing changeable components(e.g., script(s), device information, etc.) on a particular virtualgateway (e.g., virtual gateway 130′), on a particular physical gateway(e.g., gateway 130), and/or for the entire platform (e.g., for everyvirtual gateway 130′ and/or physical gateway 130 managed by platform110) or a subset of the platform (e.g., for only a portion of virtualgateways 130′ and/or physical gateways 130 managed b platform 110). Inan embodiment, scripts and/or drivers that need attention (e.g.,incomplete scripts, unverified scripts, or scripts that have generatedan error during compilation or execution on a physical gateway or as avirtual gateway), may be distinguished to a user using highlights (e.g.,bold), colors (e.g., red), marks (e.g., “!”), and/or the like.

In an embodiment, the user interface enables an entitled user to selecta particular virtual and/or physical gateway, provides a list ofcomponents on that gateway, and enables the user to edit each of thecomponents for just that gateway. In the event that the user selects avirtual gateway that is mirrored with multiple physical gateways, itshould be understood that editing the components on the virtual gatewaymay affect each of the associated mirrored physical gateways, asdiscussed elsewhere herein. In other words, a specific virtual orphysical gateway is selected, and one or more of the components on thatspecific gateway are edited.

In an alternative or additional embodiment, the user interface providesthe user with one or more inputs for identifying one or more components,identifying one or more virtual and/or physical gateways to which thecomponents are to be mirrored or copied, and initiating mirroring orcopying of the components to the identified gateway(s). Additionally,the user interface may provide the user with one or more inputs foridentifying a script stored on one or more virtual and/or physicalgateways, and initiating deletion of the script from the gateway(s).Furthermore, the user interface may provide a user, who is modifying acomponent, one or more inputs for identifying one or more virtual and/orphysical gateways to which the modifications should be applied. In otherwords, specific components are edited, specific virtual and/or physicalgateway(s) are selected or otherwise identified, and the edits areimplemented to the selected virtual and/or physical gateway(s) (e.g.,which could comprise all gateways or any subset of gateways controlledby platform 110).

In step 420, it is determined whether the user has completed theaddition, modifying, or deletion of the components (e.g., script, deviceinformation, etc.). This determination may take the form of receiving aspecific user operation (e.g., on an input of the user interface) orother indication that modification is complete or that an identifiedcomponent should be added or deleted. In other words, the process mayassume that the editing of the component is not complete until thespecific user operation is received, instead of blocking or polling.

Once the editing of the component is complete, in step 430, theapplicable virtual gateway(s) are updated to reflect the editing. If theedit only affects a single virtual gateway, only that virtual gateway isupdated. However, if the edit affects a plurality of virtual gateways,each of the plurality of virtual gateways is updated. In either case,the edits may be applied regardless of the status of the editedcomponent (e.g., irrespective of whether the component, such as ascript, is deactivated or unverified).

In step 440, it is determined whether any of the edits involve averified and/or active component or involve deleting a component from aphysical gateway. If so, synchronization with the applicable mirroredphysical gateways is performed in step 450 (e.g., by synchronizationmodule 118). Otherwise, no synchronization is necessary, since the editsmerely affect incomplete, unverified, or inactive component(s). Asdiscussed elsewhere herein, in an embodiment, incomplete, unverified,and/or inactive components may be saved in virtual gateways but notsynchronized to mirrored or selected physical gateways. In analternative embodiment, incomplete, unverified, inactive, and/or deletedcomponents may be mirrored to and/or maintained at the physicalgateway(s), but their statuses may be set to inactive to reflect thatthey are incomplete, unverified, inactive, or deleted, so that thephysical gateway(s) can handle them appropriately (e.g., by notcompiling, executing, or otherwise processing them).

It should be understood that the same process 400 can be applied toother changes made to the virtual and physical gateways. That is,process 400 can be similarly applied to user editing of components otherthan the scripts and drivers of the gateways (e.g., such as scriptengines 134 of gateways).

2.2. Synchronization

FIG. 5 illustrates a synchronization process 500, according to anembodiment. In an embodiment, process 500 may be, or be comprised in,step 450 of process 400, and may be implemented as, or as part of,synchronization module 118. Process 500 may be performed for eachvirtual and/or physical gateway requiring synchronization (e.g., eachselected or mirrored virtual gateway 130′ and/or each selected ormirrored physical gateway 130). For automated synchronization, process500 may be performed iteratively or in parallel for each gatewayrequiring synchronization

In step 510, a gateway to be synchronized is identified, andsynchronization data is received. The synchronization data may compriseany data required to synchronize the identified gateway, and can takeany variety of forms or configurations, depending on the particularimplementation. For example, in the case that a script must be added tothe gateway, the synchronization data may comprise the script. In thecase that device information (e.g., device drivers, and/or definitionsand/or configurations for devices, device types, and/or device groups)must be added to the gateway, the synchronization data may comprise thedevice information. In an embodiment, in which incremental changes canbe made to the gateway, the synchronization data may comprise arepresentation of a delta that should be applied to data stored at thegateway in order to bring it into synchronization.

In step 520, it is determined whether or not a connection (e.g.,connection 210) with the identified gateway can be or is established. Ifnot, process 500 may block until a connection can be established withthe identified gateway. In an embodiment, process 500 may wait apredetermined time before reattempting the connection. In addition, whenthe connection fails, fails a predetermined number of times, or has notbeen established after a predetermined time period, process 500 maygenerate an alert (e.g., a user interface message, email message, textmessage, etc.) to notify one or more recipients of the failure.

On the other hand, when the connection is established in step 520, theidentified gateway is synchronized in step 530. Specifically, thesynchronization data is transmitted or otherwise applied to the gateway(e.g., over network(s) 120).

2.3. Synchronization

FIG. 6 illustrates a process 640 for dereferencing wildcards in ascript, according to an embodiment. As discussed above, scripts ofvirtual gateways that are associated with multiple physical gateways maycomprise wildcards (which are dereferenced at the physical gateway),whereas scripts of virtual gateways that are only associated with asingle physical gateway may be dereferenced in the virtual gateway aswell as at the physical gateway. Process 640 may be implemented as amodule at one or more gateways 130 and/or platform 110.

In step 650, a script is received. As discussed elsewhere herein, thescript may contain wildcards, which reference generic identifiers fordevice(s), device type(s), and/or device group(s). For example, thewildcard may be asertisk(s) or other symbols added to one or morecomponents of a device, device type, or device group identifier (e.g.,added to the end of a common prefix for device, device type, or devicegroup identifiers, added to the beginning of a common suffix for device,device type, or device group identifiers). In the example of“frontdoorswitch*”, the wildcard is an asterisk added to the prefix“frontdoordevice,” indicating that wildcard represents any deviceidentifier beginning with the prefix “frontdoorswitch”, regardless ofwhat comes after that prefix in the device identifier.

In step 660, it is determined whether or not any wildcards remain in thescript being processed. If the script never contained wildcards or nolonger contains any wildcards, process 640 ends. Otherwise, the nextwildcard in the script is processed in step 670.

In step 670, a data structure comprising device, device type, or devicegroup identifiers at a particular gateway is searched using the wildcardto identify matching device, device type, or device group identifier(s).The data structure may comprise a database, table, list, object, blob,etc. In an embodiment, the wildcard represents a regular expression, anda device, device type, or device group identifier matches the wildcardif it satisfies the regular expression.

If the wildcard does not match any device, device type, or device groupidentifier(s), error processing may be performed in step 680. Errorprocessing may comprise generating an alert (e.g., a user interfacemessage, email message, text message, etc.) to notify one or morerecipients of the failure, logging the error, and/or the like.Alternatively, instead of performing error processing in step 680,process 640 may skip the unmatched wildcard, end, and/or perform otherprocessing.

If the wildcard does match a device, device type, or device groupidentifier, the wildcard is replaced in the script with the matchingdevice, device type, or device group identifier in step 690, and thenext remaining wildcard, if any, is identified in step 660. If there aremultiple matching device, device type, or device group identifiers, thewildcard may be replaced with each matching device, device type, ordevice group identifier or only a single matching device, device type,or device group identifier (e.g., the first matching device, devicetype, or device group identifier), depending on the particularimplementation of process 640.

3. Example Processing Device

FIG. 7 is a block diagram illustrating an example wired or wirelesssystem 550 that may be used in connection with various embodimentsdescribed herein. For example the system 550 may be used as or inconjunction with one or more of the mechanisms, processes, methods, orfunctions (e.g., to store and/or execute one or more software modules)described above, and may represent components of platform 110, server(s)112, gateway(s) 130, device(s) 140, user system(s) 150, and/or otherdevices described herein. The system 550 can be a server or anyconventional personal computer, or any other processor-enabled devicethat is capable of wired or wireless data communication. Other computersystems and/or architectures may be also used, as will be clear to thoseskilled in the art. In addition, it should be understood that whilesystem 550 is illustrated with certain elements, it may comprise feweror more elements than those illustrated, depending on the particularcomponent it represents. For example, a system 550 without wirelesscommunication capabilities may not include baseband 620, radio 615, andantenna 610.

The system 550 preferably includes one or more processors, such asprocessor 560. Additional processors may be provided, such as anauxiliary processor to manage input/output, an auxiliary processor toperform floating point mathematical operations, a special-purposemicroprocessor having an architecture suitable for fast execution ofsignal processing algorithms (e.g., digital signal processor), a slaveprocessor subordinate to the main processing system (e.g., back-endprocessor), an additional microprocessor or controller for dual ormultiple processor systems, or a coprocessor. Such auxiliary processorsmay be discrete processors or may be integrated with the processor 560.Examples of processors which may be used with system 550 include,without limitation, the Pentium® processor, Core i7® processor, Xeon®processor, and other models available from Intel Corporation of SantaClara, Calif., as well as hardware processors from other manufacturers,such as Advanced Micro Devices of Sunnyvale, Calif.

The processor 560 is preferably connected to a communication bus 555.The communication bus 555 may include a data channel for facilitatinginformation transfer between storage and other peripheral components ofthe system 550. In addition, the communication bus 555 may provide a setof signals used for communication with the processor 560, including adata bus, address bus, and control bus (not shown). The communicationbus 555 may comprise any standard or non-standard bus architecture suchas, for example, bus architectures compliant with industry standardarchitecture (ISA), extended industry standard architecture (EISA),Micro Channel Architecture (MCA), peripheral component interconnect(PCI) local bus, or standards promulgated by the Institute of Electricaland Electronics Engineers (IEEE) including IEEE 488 general-purposeinterface bus (GPIB), IEEE 696/S-100, and the like.

System 550 preferably includes a main memory 565 and may also include asecondary memory 570. The main memory 565 provides storage ofinstructions and data for programs executing on the processor 560, suchas one or more of the functions and/or modules discussed above. Itshould be understood that programs stored in the memory and executed byprocessor 560 may be written and/or compiled according to any suitablelanguage, including without limitation C/C++, Java, JavaScript, Perl,Visual Basic, .NET, proprietary visual scripting languages, proprietaryscripting languages, and the like. The main memory 565 is typicallysemiconductor-based memory such as dynamic random access memory (DRAM)and/or static random access memory (SRAM). Other semiconductor-basedmemory types include, for example, synchronous dynamic random accessmemory (SDRAM), Rambus dynamic random access memory (RDRAM),ferroelectric random access memory (FRAM), and the like, including readonly memory (ROM).

The secondary memory 570 may optionally include an internal memory 575and/or a removable medium 580, for example a floppy disk drive, amagnetic tape drive, a compact disc (CD) drive, a digital versatile disc(DVD) drive, other optical drive, a flash memory drive, microSD, etc.The removable medium 580 is read from and/or written to in a well-knownmanner. Removable storage medium 580 may be, for example, a floppy disk,magnetic tape, CD, DVD, SD card, thumb drive, etc.

The removable storage medium 580 is a non-transitory computer-readablemedium having stored thereon computer executable code (i.e., software)and/or data. The computer software or data stored on the removablestorage medium 580 is read into the system 550 for execution by theprocessor 560.

In alternative embodiments, secondary memory 570 may include othersimilar means for enabling computer programs or other data orinstructions to be loaded into the system 550. Such means may include,for example, an external storage medium 595 and an interface 590.Examples of external storage medium 595 may include an external harddisk drive or an external optical drive, or and external magneto-opticaldrive.

Other examples of secondary memory 570 may include semiconductor-basedmemory such as programmable read-only memory (PROM), erasableprogrammable read-only memory (EPROM), electrically erasable read-onlymemory (EEPROM), or flash memory (block-oriented memory similar toEEPROM). Also included are any other removable storage media 580 andcommunication interface 590, which allow software and data to betransferred from an external medium 595 to the system 550.

System 550 may include a communication interface 590. The communicationinterface 590 allows software and data to be transferred between system550 and external devices (e.g. printers), networks, or informationsources. For example, computer software or executable code may betransferred to system 550 from a network or cloud server viacommunication interface 590. Examples of communication interface 590include a built-in network adapter, network interface card (NIC),Personal Computer Memory Card International Association (PCMCIA) networkcard, card bus network adapter, wireless network adapter, UniversalSerial Bus (USB) network adapter, modem, a network interface card (NIC),a wireless data card, a communications port, an infrared interface, anIEEE 1394 fire-wire, or any other device capable of interfacing system550 with a network or another computing device.

Communication interface 590 preferably implements industry-promulgatedprotocol standards, such as Ethernet IEEE 802 standards, Fiber Channel,digital subscriber line (DSL), asynchronous digital subscriber line(ADSL), frame relay, asynchronous transfer mode, integrated digitalservices network (ISDN), personal communications services (PCS),transmission control protocol/Internet protocol (TCP/IP), serial lineInternet protocol/point to point protocol (SLIP/PPP), and so on, but mayalso implement customized or non-standard interface protocols as well.

Software and data transferred via communication interface 590 aregenerally in the form of electrical communication signals 605. Thesesignals 605 are preferably provided to communication interface 590 via acommunication channel 600. In one embodiment, the communication channel600 may be a wired or wireless network, or any variety of othercommunication links. Communication channel 600 carries signals 605 andcan be implemented using a variety of wired or wireless communicationmeans including wire or cable, fiber optics, conventional phone line,cellular phone link, wireless data communication link, radio frequency(“RF”) link, or infrared link, just to name a few.

Computer executable code (i.e., computer programs or software, such asthe disclosed application) is stored in the main memory 565 and/or thesecondary memory 570. Computer programs can also be received viacommunication interface 590 and stored in the main memory 565 and/or thesecondary memory 570. Such computer programs, when executed, enable thesystem 550 to perform the various functions of the present invention aspreviously described.

In this description, the terms “computer-readable medium,” “storagemedium,” and “medium” are used to refer to any non-transitory computerreadable storage media used to provide computer executable code (e.g.,software and computer programs) to the system 550. Examples of thesemedia include main memory 565, secondary memory 570 (including internalmemory 575, removable medium 580, and external storage medium 595), andany peripheral device communicatively coupled with communicationinterface 590 (including a network information server or other networkdevice). These non-transitory computer readable mediums are means forproviding executable code, programming instructions, and software to thesystem 550.

In an embodiment that is implemented using software, the software may bestored on a computer-readable medium and loaded into the system 550 byway of removable medium 580, I/O interface 585, or communicationinterface 590. In such an embodiment, the software is loaded into thesystem 550 in the form of electrical communication signals 605. Thesoftware, when executed by the processor 560, preferably causes theprocessor 560 to perform the inventive features and functions previouslydescribed herein.

In an embodiment, I/O interface 585 provides an interface between one ormore components of system 550 and one or more input and/or outputdevices. Example input devices include, without limitation, keyboards,touch screens or other touch-sensitive devices, biometric sensingdevices, computer mice, trackballs, pen-based pointing devices, and thelike. Examples of output devices include, without limitation, cathoderay tubes (CRTs), plasma displays, light-emitting diode (LED) displays,liquid crystal displays (LCDs), printers, vacuum florescent displays(VFDs), surface-conduction electron-emitter displays (SEDs), fieldemission displays (FEDs), and the like.

The system 550 also includes optional wireless communication componentsthat facilitate wireless communication over a voice and over a datanetwork. The wireless communication components comprise an antennasystem 610, a radio system 615 and a baseband system 620. In the system550, radio frequency (RF) signals are transmitted and received over theair by the antenna system 610 under the management of the radio system615.

In one embodiment, the antenna system 610 may comprise one or moreantennae and one or more multiplexors (not shown) that perform aswitching function to provide the antenna system 610 with transmit andreceive signal paths. In the receive path, received RF signals can becoupled from a multiplexor to a low noise amplifier (not shown) thatamplifies the received RF signal and sends the amplified signal to theradio system 615.

In alternative embodiments, the radio system 615 may comprise one ormore radios that are configured to communicate over various frequenciesand protocols. In one embodiment, the radio system 615 may combine ademodulator (not shown) and modulator (not shown) in one integratedcircuit (IC). The demodulator and modulator can also be separatecomponents. In the incoming path, the demodulator strips away the RFcarrier signal leaving a baseband receive audio signal, which is sentfrom the radio system 615 to the baseband system 620.

If the received signal contains audio information, then baseband system620 decodes the signal and converts it to an analog signal. Then thesignal is amplified and sent to a speaker. The baseband system 620 alsoreceives analog audio signals from a microphone. These analog audiosignals are converted to digital signals and encoded by the basebandsystem 620. The baseband system 620 also codes the digital signals fortransmission and generates a baseband transmit audio signal that isrouted to the modulator portion of the radio system 615. The modulatormixes the baseband transmit audio signal with an RF carrier signalgenerating an RF transmit signal that is routed to the antenna systemand may pass through a power amplifier (not shown). The power amplifieramplifies the RF transmit signal and routes it to the antenna system 610where the signal is switched to the antenna port for transmission.

The baseband system 620 is also communicatively coupled with theprocessor 560. The central processing unit 560 has access to datastorage areas 565 and 570. The central processing unit 560 is preferablyconfigured to execute instructions (i.e., computer programs or software)that can be stored in the memory 565 or the secondary memory 570.Computer programs can also be received from the baseband processor 610and stored in the data storage area 565 or in secondary memory 570, orexecuted upon receipt. Such computer programs, when executed, enable thesystem 550 to perform the various functions of the present invention aspreviously described. For example, data storage areas 565 may includevarious software modules (not shown).

Various embodiments may also be implemented primarily in hardware using,for example, components such as application specific integrated circuits(ASICs), or field programmable gate arrays (FPGAs). Implementation of ahardware state machine capable of performing the functions describedherein will also be apparent to those skilled in the relevant art.Various embodiments may also be implemented using a combination of bothhardware and software.

Furthermore, those of skill in the art will appreciate that the variousillustrative logical blocks, modules, circuits, and method stepsdescribed in connection with the above described figures and theembodiments disclosed herein can often be implemented as electronichardware, computer software, or combinations of both. To clearlyillustrate this interchangeability of hardware and software, variousillustrative components, blocks, modules, circuits, and steps have beendescribed above generally in terms of their functionality. Whether suchfunctionality is implemented as hardware or software depends upon theparticular application and design constraints imposed on the overallsystem. Skilled persons can implement the described functionality invarying ways for each particular application, but such implementationdecisions should not be interpreted as causing a departure from thescope of the invention. In addition, the grouping of functions within amodule, block, circuit or step is for ease of description. Specificfunctions or steps can be moved from one module, block or circuit toanother without departing from the invention.

Moreover, the various illustrative logical blocks, modules, functions,and methods described in connection with the embodiments disclosedherein can be implemented or performed with a general purpose processor,a digital signal processor (DSP), an ASIC, FPGA, or other programmablelogic device, discrete gate or transistor logic, discrete hardwarecomponents, or any combination thereof designed to perform the functionsdescribed herein. A general-purpose processor can be a microprocessor,but in the alternative, the processor can be any processor, controller,microcontroller, or state machine. A processor can also be implementedas a combination of computing devices, for example, a combination of aDSP and a microprocessor, a plurality of microprocessors, one or moremicroprocessors in conjunction with a DSP core, or any other suchconfiguration.

Additionally, the steps of a method or algorithm described in connectionwith the embodiments disclosed herein can be embodied directly inhardware, in a software module executed by a processor, or in acombination of the two. A software module can reside in RAM memory,flash memory, ROM memory, EPROM memory, EEPROM memory, registers, harddisk, a removable disk, a CD-ROM, or any other form of storage mediumincluding a network storage medium. An exemplary storage medium can becoupled to the processor such that the processor can read informationfrom, and write information to, the storage medium. In the alternative,the storage medium can be integral to the processor. The processor andthe storage medium can also reside in an ASIC.

Any of the software components described herein may take a variety offorms. For example, a component may be a stand-alone software package,or it may be a software package incorporated as a “tool” in a largersoftware product. It may be downloadable from a network, for example, awebsite, as a stand-alone product or as an add-in package forinstallation in an existing software application. It may also beavailable as a client-server software application, as a web-enabledsoftware application, and/or as a mobile application.

The above description of the disclosed embodiments is provided to enableany person skilled in the art to make or use the invention. Variousmodifications to these embodiments will be readily apparent to thoseskilled in the art, and the general principles described herein can beapplied to other embodiments without departing from the spirit or scopeof the invention. Thus, it is to be understood that the description anddrawings presented herein represent a presently preferred embodiment ofthe invention and are therefore representative of the subject matterwhich is broadly contemplated by the present invention. It is furtherunderstood that the scope of the present invention fully encompassesother embodiments that may become obvious to those skilled in the artand that the scope of the present invention is accordingly not limited.

What is claimed is:
 1. A system comprising: at least one hardwareprocessor; and a memory storing one or more software modules that, whenexecuted by the at least one hardware processor, generate a virtualgateway which comprises a representation of each of one or more activescripts stored on at least one remote physical gateway, wherein the oneor more active scripts are configured to monitor or control one or moreexternal devices communicatively connected to the at least one remotephysical gateway, wherein at least one of the one or more active scriptsrepresented in the virtual gateway comprises one or more genericidentifiers for at least one of the one or more external devices, andwherein each of the one or more generic identifiers comprises one ormore wildcards; provide at least one user interface for editing each ofthe one or more active scripts represented in the virtual gateway; andautomatically maintain synchronization, across at least one network,between the one or more active scripts represented in the virtualgateway and the one or more active scripts stored on the at least oneremote physical gateway.
 2. The system of claim 1, wherein the virtualgateway further comprises a representation of each of one or more activedrivers stored on the at least one remote physical gateway, and whereinthe one or more software modules further: provide at least one userinterface for editing each of the one or more active drivers representedin the virtual gateway; and automatically maintain synchronization,across the at least one network, between the one or more active driversrepresented in the virtual gateway and the one or more active driversstored on the at least one remote physical gateway.
 3. The system ofclaim 1, wherein the one or more software modules are comprised in thememory in a server and further: detect a failure of the at least oneremote physical gateway; and, in response to the failure of the at leastone remote physical gateway, locally execute the one or more activescripts represented in the virtual gateway at the server instead of atthe at least one remote physical gateway.
 4. The system of claim 1,wherein the at least one remote physical gateway comprises a pluralityof remote physical gateways associated with the virtual gateway, andwherein the one or more software modules further automatically maintainsynchronization, across the at least one network, between the one ormore active scripts represented in the virtual gateway and the one ormore active scripts stored on each of the plurality of remote physicalgateways.
 5. The system of claim 4, wherein the at least one userinterface comprises one or more inputs for selecting the plurality ofremote physical gateways to be associated with the virtual gateway. 6.The system of claim 5, wherein selecting the plurality of remotephysical gateways comprises selecting a type of remote physical gateway,and wherein the one or more software modules automatically adds allremote physical gateways of the selected type to the plurality of remotephysical gateways associated with the virtual gateway.
 7. The system ofclaim 5, wherein selecting the plurality of remote physical gatewayscomprises selecting a grouping of remote physical gateways, and whereinthe one or more software modules automatically adds all remote physicalgateways in the grouping to the plurality of remote physical gatewaysassociated with the virtual gateway.
 8. The system of claim 1, whereinthe virtual gateway further comprises a representation of each of one ormore inactive scripts which are not synchronized with any scripts storedon the at least one remote physical gateway.
 9. The system of claim 1,further comprising the at least one remote physical gateway, wherein theat least one remote physical gateway comprises at least one moduleconfigured to dereference the at least one active script by, for each ofthe one or more generic identifiers in the at least one active script:identify at least one of the one or more external devices having adevice identifier that matches the generic identifier; and replace thegeneric identifier with the device identifier of the identified at leastone device.
 10. The system of claim 1, further comprising the at leastone remote physical gateway, wherein the at least one remote physicalgateway comprises: a compiler configured to compile the one or moreactive scripts into one or more virtual-machine codes; and a virtualmachine configured to execute the one or more virtual-machine codes. 11.The system of claim 1, wherein the virtual gateway further comprises arepresentation of each of one or more inactive scripts, wherein the atleast one user interface comprises one or more inputs by which a usermay specify whether or not the one or more inactive scripts are to besynchronized, and wherein the one or more software modules, when theuser specifies that the one or more inactive scripts are to besynchronized, automatically maintains synchronization, across the atleast one network, between the one or more inactive scripts representedin the virtual gateway and one or more inactive scripts stored on the atleast one remote physical gateway.
 12. The system of claim 1, whereinthe at least one user interface comprises one or more inputs forswitching each of the one or more active scripts into an inactive scriptand switching each inactive script into an active script.
 13. The systemof claim 1, wherein the memory stores a library of scripts, wherein theat least one user interface comprises one or more inputs for selecting ascript to add to the virtual gateway from the library of scripts, andwherein the one or more software modules add a representation of theselected script to the virtual gateway.
 14. The system of claim 1,wherein editing the one or more active scripts comprises changing one ormore of a trigger, condition, and referenced device within the one ormore active scripts.
 15. The system of claim 1, wherein the at least oneuser interface for editing each of the one or more active scriptscomprises one or more inputs for switching an active script into aninactive script and switching an inactive script into an active script.16. A method for managing a gateway, the method comprising using atleast one hardware processor to: generate a virtual gateway whichcomprises a representation of each of one or more active scripts storedon at least one remote physical gateway, wherein the one or more activescripts are configured to monitor or control one or more externaldevices communicatively connected to the at least one remote physicalgateway, wherein at least one of the one or more active scriptsrepresented in the virtual gateway comprises one or more genericidentifiers for at least one of the one or more external devices, andwherein each of the one or more generic identifiers comprises one ormore wildcards; provide at least one user interface for editing each ofthe one or more active scripts represented in the virtual gateway; andautomatically maintain synchronization, across at least one network,between the one or more active scripts represented in the virtualgateway and the one or more active scripts stored on the at least oneremote physical gateway.
 17. The method of claim 16, wherein the virtualgateway further comprises a representation of each of one or more activedrivers stored on the at least one remote physical gateway, and whereinthe method further comprise using the at least one hardware processorto: provide at least one user interface for editing each of the one ormore active drivers represented in the virtual gateway; andautomatically maintain synchronization, across the at least one network,between the one or more active drivers represented in the virtualgateway and the one or more active drivers stored on the at least oneremote physical gateway.
 18. The method of claim 16, further comprisingusing the at least one hardware processor at a server to: detect afailure of the at least one remote physical gateway; and, in response tothe failure of the at least one remote physical gateway, locally executethe one or more active scripts represented in the virtual gateway at theserver instead of at the at least one remote physical gateway.
 19. Themethod of claim 16, wherein the at least one remote physical gatewaycomprises a plurality of remote physical gateways associated with thevirtual gateway, and wherein the method comprises using the at least onehardware processor to automatically maintain synchronization, across theat least one network, between the one or more active scripts representedin the virtual gateway and the one or more active scripts stored on eachof the plurality of remote physical gateways.
 20. The method of claim16, wherein the virtual gateway further comprises a representation ofeach of one or more inactive scripts which are not synchronized with anyscripts stored on the at least one remote physical gateway.
 21. Anon-transitory computer-readable medium having instructions storedthereon, wherein the instructions, when executed by a processor, causethe processor to: generate a virtual gateway which comprises arepresentation of each of one or more active scripts stored on at leastone remote physical gateway, wherein the one or more active scripts areconfigured to monitor or control one or more external devicescommunicatively connected to the at least one remote physical gateway,wherein at least one of the one or more active scripts represented inthe virtual gateway comprises one or more generic identifiers for atleast one of the one or more external devices, and wherein each of theone or more generic identifiers comprises one or more wildcards; provideat least one user interface for editing each of the one or more activescripts represented in the virtual gateway; and automatically maintainsynchronization, across at least one network, between the one or moreactive scripts represented in the virtual gateway and the one or moreactive scripts stored on the at least one remote physical gateway.